Information management change deployment system

ABSTRACT

A method for managing information relating to a change deployment in order to communicate some or all the information to a plurality of users includes providing an interface to users at workstations accessible by the users, receiving information comprising a plurality of messages from users communicating via the workstations during a change deployment session, initiating display of at least one of the messages to the users via the interface, initiating display of task data to the users via the interface, the task data corresponding to at least one task necessary for completing the change deployment, logging event data related to a plurality of events associated with the change deployment conference session, the event data comprising task status data indicating the status of the at least one task necessary for completing the change deployment, and initiating display of at least some of the event data to the users via the interface.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/027,965, filed Feb. 15, 2011; the contents of which are herebyincorporated by reference.

FIELD

In general, embodiments of the invention relate to systems forinformation management. More specifically, embodiments of the inventionrelate to systems for information management related to changedeployment.

BACKGROUND

In recent history, teleconferencing has become possible, and evenrelatively affordable, across continents and among large numbers ofparticipants. In large organizations, particularly during line ofbusiness-wide or even organization-wide initiatives, suchteleconferences can cover a broad and deep range of topics, such asaddressing potential problems facing lines of business within theorganization or the organization as a whole. As a result, organizationalteleconferences often require participation from many different lines ofbusiness within an organization, and in some instances requireparticipation from many individuals within a line of businessrepresenting differing levels of management responsibility.

Similar to the field of teleconferencing is the somewhat newer area oftextual chatting via the Internet. Chat rooms provide a conduit forindividuals to communicate with one another, generally concerning apre-defined topic of discussion. For example, an Internet chat room mayprovide individuals an opportunity to post messages regarding theirfavorite sports team for consideration and response from otherindividuals participating in the same chat room.

However, neither modern teleconferencing nor modern chattingtechnologies provide an interface for individuals participating incompleted, ongoing or future problem initiative, change initiative ororganization-wide, multiple change initiative projects. Neither domodern teleconferencing or chatting technologies provide an interfacefor relating information through which the individual can quickly andeasily ascertain the status of the project. For these and other reasons,an interface configured for providing numerous supplemental functionssuch as, for example, initiating display of the status of an ongoingissue discussed during the teleconference, is needed.

BRIEF SUMMARY

The following presents a simplified summary of one or more embodimentsof the invention in order to provide a basic understanding of suchembodiments. This summary is not an extensive overview of allcontemplated embodiments, and is intended to neither identify key orcritical elements of all embodiments, nor delineate the scope of any orall embodiments. Its sole purpose is to present some concepts of one ormore embodiments in a simplified form as a prelude to the more detaileddescription that is presented later.

According to embodiments of the invention, a method A method formanaging information that relates to a change deployment in order tocommunicate some or all the information to a plurality of users. Themethod includes providing an interface, using a processing device, to aplurality of users at a plurality of workstations accessible by one ormore of the users, receiving information comprising a plurality ofmessages from users communicating via the workstations during a changedeployment session, initiating display of at least one of the pluralityof messages to the users via the interface, initiating display of taskdata to the users via the interface, the task data corresponding to atleast one task necessary for completing the change deployment, loggingevent data related to a plurality of events associated with the changedeployment conference session, the event data comprising task statusdata indicating the status of the at least one task necessary forcompleting the change deployment, and initiating display of at leastsome of the event data to the users via the interface.

In some embodiments, the event data comprises data corresponding to oneor more messages received from one or more users. In some embodiments,the interface comprises a first panel and a second panel, the firstpanel configured for displaying at least some of the event data and thesecond panel configured for displaying at least one of the plurality ofmessages. In some embodiments, the plurality of messages comprises adialogue among the plurality of users and wherein the event datacorresponds to the dialogue, wherein logging the event data compriseslogging data related to the dialogue and wherein initiating display ofat least some of the event data comprises initiating display of at leasta portion of the logged dialogue. In some embodiments, the method alsoincludes archiving at least a portion of the logged event data, whereinthe archived data is configured as searchable and retrievable data. Insome embodiments, the method also includes initiating communication ofan alert comprising information corresponding to an event related tologged event data. In some such embodiments, initiating communicationcomprises one of initiating a pager alert, initiating a text messagealert, initiating an email alert, initiating social media status update,or initiating a social media message.

In some embodiments, the method also includes initiating preparation ofa report based at least in part on at least a portion of the loggedevent data or at least one of the received messages. In someembodiments, the method also includes initiating a second interface inresponse to a request from a user, the second interface configured forreceiving a plurality of messages from one or more of the plurality ofusers. In some embodiments, the interface comprises a first panel and asecond panel, the first panel configured for displaying at least one ofthe plurality of messages and the second panel configured for displayinga list of users participating in the conference session.

In some embodiments, the interface comprises a first panel, a secondpanel and a third panel, the first panel configured for displaying atleast some of the event data, the second panel configured for displayingat least one of the plurality of messages, and the third panelconfigured for displaying a list of user participating in the conferencesession. In some such embodiments, the first panel is disposed on theleft-hand side of the second panel and the third panel is disposed onthe right-hand side of the second panel.

In some embodiments, the method also includes retrieving archived datafrom a database in response to a request from a user participating inthe conference session, the archived data corresponding to a previouslyconducted conference session.

In some embodiments, the method also includes logging session datarelated to the conference session and initiating display of at leastsome of the session data via the interface. In some such embodiments,the session data comprises data corresponding to an overall status ofthe change deployment being addressed by the conference session, changedeployment identification information, or change deployment summaryinformation. In some of those embodiments, the method also includesinitiating preparation of a report based at least in part on at least aportion of the data corresponding to an overall status of the changedeployment being addressed by the conference session, change deploymentidentification information, or change deployment summary information.

In some embodiments, the method includes initiating display of aplurality of required participants and the status of each of theplurality of required participants.

According to embodiments of the invention, a system for managinginformation relating to a change deployment in order to communicate someor all the information to a plurality of users has a processing device.The processing device is configured for providing an interface to aplurality of users at a plurality of workstations accessible by one ormore of the users, receiving information comprising a plurality ofmessages from users communicating via the workstations during a changedeployment session, initiating display of at least one of the pluralityof messages to the users via the interface, initiating display of taskdata to the users via the interface, the task data corresponding to atleast one task necessary for completing the change deployment, loggingevent data related to a plurality of events associated with the changedeployment conference session, the event data comprising task statusdata indicating the status of the at least one task necessary forcompleting the change deployment, and initiating display of at leastsome of the event data to the users via the interface.

In some embodiments, the event data comprises data corresponding to oneor more messages received from one or more users. In some embodiments,the interface comprises a first panel and a second panel, the firstpanel configured for displaying at least some of the event data and thesecond panel configured for displaying at least one of the plurality ofmessages. In some embodiments, the plurality of messages comprises adialogue among the plurality of users and wherein the event datacorresponds to the dialogue, wherein logging the event data compriseslogging data related to the dialogue and wherein initiating display ofat least some of the event data comprises initiating display of at leasta portion of the logged dialogue. In some embodiments, the processingdevice is further configured for archiving at least a portion of thelogged event data, wherein the archived data is configured as searchableand retrievable data.

In some embodiments, the processing device is further configured forinitiating communication of an alert comprising informationcorresponding to an event related to logged event data. In some suchembodiments, initiating communication comprises one of initiating apager alert, initiating a text message alert, initiating an email alert,initiating social media status update, or initiating a social mediamessage.

In some embodiments, the processing device is further configured forinitiating preparation of a report based at least in part on at least aportion of the logged event data or at least one of the receivedmessages. In some embodiments, the processing device is furtherconfigured for initiating a second interface in response to a requestfrom a user, the second interface configured for receiving a pluralityof messages from one or more of the plurality of users. In someembodiments, the interface comprises a first panel and a second panel,the first panel configured for displaying at least one of the pluralityof messages and the second panel configured for displaying a list ofusers participating in the conference session.

In some embodiments, the interface comprises a first panel, a secondpanel and a third panel, the first panel configured for displaying atleast some of the event data, the second panel configured for displayingat least one of the plurality of messages, and the third panelconfigured for displaying a list of user participating in the conferencesession. In some such embodiments, the first panel is disposed on theleft-hand side of the second panel and the third panel is disposed onthe right-hand side of the second panel.

In some embodiments, the processing device is further configured forretrieving archived data from a database in response to a request from auser participating in the conference session, the archived datacorresponding to a previously conducted conference session.

In some embodiments, the processing device is further configured forlogging session data related to the conference session and initiatingdisplay of at least some of the session data via the interface. In somesuch embodiments, the session data comprises data corresponding to anoverall status of the change deployment being addressed by theconference session, change deployment identification information, orchange deployment summary information. In some of those embodiments, theprocessing device is further configured for initiating preparation of areport based at least in part on at least a portion of the datacorresponding to an overall status of the change deployment beingaddressed by the conference session, change deployment identificationinformation, or change deployment summary information.

In some embodiments, the processing device is further configured forinitiating display of a plurality of required participants and thestatus of each of the plurality of required participants.

According to embodiments of the invention, a computer program productincludes a non-transient computer-readable memory havingcomputer-executable instructions for managing information relating to achange deployment in order to communicate some or all the information toa plurality of users. The instructions include instructions forproviding an interface to a plurality of users at a plurality ofworkstations accessible by one or more of the users, instructions forreceiving information comprising a plurality of messages from userscommunicating via the workstations during a change deployment session,instructions for initiating display of at least one of the plurality ofmessages to the users via the interface, instructions for initiatingdisplay of task data to the users via the interface, the task datacorresponding to at least one task necessary for completing the changedeployment, instructions for logging event data related to a pluralityof events associated with the change deployment conference session, theevent data comprising task status data indicating the status of the atleast one task necessary for completing the change deployment, andinstructions for initiating display of at least some of the event datato the users via the interface.

In some embodiments, the event data comprises data corresponding to oneor more messages received from one or more users. In some embodiments,the interface comprises a first panel and a second panel, the firstpanel configured for displaying at least some of the event data and thesecond panel configured for displaying at least one of the plurality ofmessages. In some embodiments, the plurality of messages comprises adialogue among the plurality of users and wherein the event datacorresponds to the dialogue, wherein the instructions for logging theevent data comprise instructions for logging data related to thedialogue and wherein the instructions for initiating display of at leastsome of the event data comprise instructions for initiating display ofat least a portion of the logged dialogue. In some embodiments, theinstructions further comprise instructions for archiving at least aportion of the logged event data, wherein the archived data isconfigured as searchable and retrievable data.

In some embodiments, the instructions also include instructions forinitiating communication of an alert comprising informationcorresponding to an event related to logged event data. In some suchembodiments, the instructions for initiating communication comprise oneof instructions for initiating a pager alert, instructions forinitiating a text message alert, instructions for initiating an emailalert, instructions for initiating social media status update, orinstructions for initiating a social media message.

In some embodiments, the instructions further comprise instructions forinitiating preparation of a report based at least in part on at least aportion of the logged event data or at least one of the receivedmessages. In some embodiments, the instructions further compriseinstructions for initiating a second interface in response to a requestfrom a user, the second interface configured for receiving a pluralityof messages from one or more of the plurality of users. In someembodiments, the interface comprises a first panel and a second panel,the first panel configured for displaying at least one of the pluralityof messages and the second panel configured for displaying a list ofusers participating in the conference session. In some embodiments, theinterface comprises a first panel, a second panel and a third panel, thefirst panel configured for displaying at least some of the event data,the second panel configured for displaying at least one of the pluralityof messages, and the third panel configured for displaying a list ofuser participating in the conference session. In some embodiments, thefirst panel is disposed on the left-hand side of the second panel andthe third panel is disposed on the right-hand side of the second panel.In some embodiments, the instructions further comprise instructions forretrieving archived data from a database in response to a request from auser participating in the conference session, the archived datacorresponding to a previously conducted conference session.

In some embodiments, the instructions further comprise instructions forlogging session data related to the conference session and initiatingdisplay of at least some of the session data via the interface. In somesuch embodiments, the session data comprises data corresponding to anoverall status of the change deployment being addressed by theconference session, change deployment identification information, orchange deployment summary information. In some of those embodiments, theinstructions further comprise instructions for initiating preparation ofa report based at least in part on at least a portion of the datacorresponding to an overall status of the change deployment beingaddressed by the conference session, change deployment identificationinformation, or change deployment summary information.

In some embodiments, the instructions further comprise instructions forinitiating display of a plurality of required participants and thestatus of each of the plurality of required participants.

According to embodiments of the invention, a method for managinginformation relating to a change deployment in order to communicate someof all the information to a plurality of users includes receiving aplurality of messages from a plurality of users communicating via aplurality of workstations during a change deployment session, theplurality of messages comprising a dialogue among the plurality of usersand initiating, by a processing device, an interface to one or more ofthe plurality of users. Initiating the interface includes initiatingdisplay of at least one of the plurality of messages to the users viathe interface and initiating display of task data to the users via theinterface, the task data corresponding to at least one task necessaryfor completing the change deployment. The method also includes loggingevent data related to a plurality of events associated with the changedeployment session, the event data comprising task status dataindicating the status of the at least one task necessary for completingthe change deployment, logging session data comprising datacorresponding to an overall status of the change deployment beingaddressed by the session, change deployment identification information,or change deployment summary information, and archiving at least aportion of the logged event data, wherein the archived data isconfigured as searchable and retrievable data. Initiating presentationof the interface further comprises initiating display of at least someof the event data and at least some of the session data to the users viathe interface.

In some embodiments, the method also includes initiating communicationof an alert comprising information corresponding to an event related tologged event data. In some embodiments, initiating communicationcomprises one of initiating a pager alert, initiating a text messagealert, initiating an email alert, initiating social media status update,or initiating a social media message. In some embodiments, the methodalso includes initiating preparation of a report based at least in parton at least a portion of the logged event data or at least one of thereceived messages. In some embodiments, the method also includesinitiating a second interface in response to a request from a user, thesecond interface configured for receiving a plurality of messages fromone or more of the plurality of users. In some embodiments, theinterface comprises a first panel, a second panel and a third panel, thefirst panel configured for displaying at least some of the event data,the second panel configured for displaying at least one of the pluralityof messages, and the third panel configured for displaying a list ofusers participating in the session. In some embodiments, the method alsoincludes initiating preparation of a report based at least in part on atleast a portion of the data corresponding to an identification of aproblem being addressed by the conference session, a status of theproblem being addressed by the conference session, or a status of one ormore solutions or solution steps proposed to address the problem.

According to embodiments of the invention, a system for managinginformation relating to a change deployment in order to communicate someor all the information to a plurality of users includes a processingdevice. The processing device is configured for receiving a plurality ofmessages from a plurality of users communicating via a plurality ofworkstations during a change deployment session, the plurality ofmessages comprising a dialogue among the plurality of users andinitiating an interface to one or more of the plurality of users.Initiating an interface includes initiating display of at least one ofthe plurality of messages to the users via the interface and initiatingdisplay of task data to the users via the interface, the task datacorresponding to at least one task necessary for completing the changedeployment. The processing device is further configured for loggingevent data related to a plurality of events associated with the changedeployment session, the event data comprising task status dataindicating the status of the at least one task necessary for completingthe change deployment, logging session data comprising datacorresponding to an overall status of the change deployment beingaddressed by the session, change deployment identification information,or change deployment summary information, and archiving at least aportion of the logged event data, wherein the archived data isconfigured as searchable and retrievable data. Initiating presentationof the interface also includes initiating display of at least some ofthe event data and at least some of the session data to the users viathe interface.

The following description and the annexed drawings set forth in detailcertain illustrative features of one or more embodiments of theinvention. These features are indicative, however, of but a few of thevarious ways in which the principles of various embodiments may beemployed, and this description is intended to include all suchembodiments and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described embodiments of the invention in general terms,reference will now be made to the accompanying drawings, wherein:

FIGS. 1A and 1B are flowcharts illustrating methods for informationmanagement related to a problem definition initiative according toembodiments of the invention;

FIGS. 2A and 2B are flowcharts illustrating methods for informationmanagement related to a change deployment according to embodiments ofthe invention;

FIGS. 3A, 3B, and 3C are flowcharts illustrating methods for informationmanagement related to deployment of a plurality of changes according toembodiments of the invention;

FIG. 4 is a block diagram of an environment in which an informationmanagement system operates and communicates across a network accordingto embodiments of the invention;

FIGS. 5A, 5B, 5C, 5D, and 5E are illustrations of screenshots of aproblem interface of an information management system according toembodiments of the invention;

FIGS. 6A, 6B, 6C, 6D, and 6E are illustrations of screenshots of achange interface of an information management system according toembodiments of the invention; and

FIGS. 7A.1, 7A.2, 7B, 7C, 7D, 7E and 7F are illustrations of screenshotsof a detailed task scheduler (DTS) interface of an informationmanagement system according to embodiments of the invention.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

Embodiments of the present invention will now be described more fullyhereinafter with reference to the accompanying drawings, in which some,but not all, embodiments of the invention are shown. Indeed, theinvention may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure will satisfy applicablelegal requirements. Like numbers refer to like elements throughout.

According to embodiments of the invention, an information managementsystem includes, in various embodiments, multiple components. Forexample, in some embodiments, the information management system includesa problem component, a change component and a detailed task scheduler(DTS) component. In some embodiments, each of the components is embodiedin an application stored on or near the information management system,such as within computer-readable instructions stored in a memory deviceof the information management system as discussed further below. Thevarious components are presented to users through a one or moreinterfaces corresponding to the components of the system and theirapplications. The user typically accesses the information managementsystem remotely from a workstation across a network, such as an intranetor the Internet or a combination. Accordingly, the problem component ofthe system is presented to users as a problem interface as discussedbelow, the change component is presented to users as a change interfaceas discussed below, and the DTS component is presented to users as a DTSinterface as discussed below. Each of the interfaces providesinformation regarding its subject matter and is also configured forreceiving user input in a variety of ways.

The problem interface, in some embodiments, is configured for providingusers access to information concerning a problem definition initiative,that is, during an effort to determine detailed information regarding aproblem facing an organization and/or its lines of business. In someinstances the term “problem” also refers to a business issue beingconsidered for resolution, a stratagem being considered forimplementation, infrastructure being considered for installation, one ormore changes being considered for deployment, and/or the like. Thechange interface, in some embodiments, is configured for providing usersaccess to information concerning a change either scheduled fordeployment within the organization, during deployment orpost-deployment. The DTS interface, in some embodiments, is configuredfor providing users access to information regarding a multiple changedeployment or release. A change, for example, may refer to installationof a software application on the workstations within particular lines ofbusiness within an organization. A release refers to a project involvingrelease of multiple changes. Such a release is typically performedacross an entire organization or across large entities or groups ofentities within an organization. Thus, the DTS interface allows users toaccess information regarding many different changes scheduled to takeplace, during the release itself, or after the release has occurred. Invarious embodiments of the problem interface, the change interface,and/or the DTS interface, summary or session information of a generalnature can be provided to users, a dialogue or chatting function can beprovided as well as listings of active and scheduled participants can beprovided. The summary or session information can include, in variousembodiments, information regarding one or more bridgeline conferenceseither scheduled or ongoing that are associated with the subject matterof the interface session(s), that is, associated with the particularproblem under consideration, the particular change being deployed,and/or the particular release scheduled or underway. In this regard, theinformation management system provides its users a centralizedrepository of real-time, up-to-date information regarding the probleminitiative, the change deployment and/or the release as well as theability to interact with one another. In some embodiments, theinterfaces provide users an opportunity to come up to speed on an issuebefore joining in a teleconference or other dialogue, thereby improvingefficiency during the teleconference or dialogue.

Generally speaking, an initiative refers to an effort with regard to anissue being addressed, such as a problem, change deployment or multiplechange deployment. A session may be or include, for example, a probleminterface, a change interface, or a DTS interface being provided by thesystem as a tool used during the initiative. In some embodiments, asession may also include a dialogue such as a teleconference or chat,and in some such embodiments, the interface provided by the systemfacilitates such dialogue. For example, an administrator initiates aproblem interface associated with a particular problem initiative andsuch a problem interface may be referred to as a problem definitioninitiative session. A session may begin before, during or after dialogueand/or teleconferencing regarding a particular issue or initiativeand/or may end before, during or after dialogue and/or teleconferencingregarding a particular issue or initiative. In some embodiments, asession may begin and/or end before, during or after definition of aproblem is complete, deployment of a change is complete and/ordeployment of multiple changes is complete.

According to embodiments of the invention, a method and system manageinformation relating to a change deployment in order to communicate someor all the information to a plurality of users. The method includesproviding an interface to users at workstations accessible by the users,receiving information comprising a plurality of messages from userscommunicating via the workstations during a change deployment session,initiating display of at least one of the messages to the users via theinterface, initiating display of task data to the users via theinterface, the task data corresponding to at least one task necessaryfor completing the change deployment, logging event data related to aplurality of events associated with the change deployment conferencesession, the event data comprising task status data indicating thestatus of the at least one task necessary for completing the changedeployment, and initiating display of at least some of the event data tothe users via the interface.

Referring now to FIG. 1A, a flowchart illustrates a method 100A forinformation management related to a problem definition initiative. Aproblem definition initiative refers to the effort within anorganization to define a problem. More specifically, a problemdefinition initiative includes some or all the meetings, conferences,communication sessions, such as those carried out via the probleminterface of the invention, and the like. The first step in the method100A, as represented by block 110 is receiving information comprising aplurality of messages from a plurality of users communicating via aplurality of workstations during a problem definition initiativesession. The plurality of messages, in some instances, comprise and/orare referred to as a dialogue, chat or chatting session. The messages,in various embodiments, include status messages, for example, regardingthe users of the interface or messages generated by one or more of theusers of the interface. For example, a user may post informationregarding details regarding the problem so that the other users canreview the information. The next step, as represented by block 120 isinitiating an interface to one or more of the plurality of usersincluding initiating display of at least one of a plurality of messagesvia the interface on a viewing device such as a computer monitor,personal digital assistance, other mobile device, or the like.

The interface, for example, in some embodiments, includes two or morepanels, such as panels vertically dividing the user's display. In oneexample embodiment, a first panel is configured for displaying at leastsome of the event data on the left-hand side of the display, a secondpanel is configured for displaying at least one of the plurality ofmessages in the middle of the display, and a third panel is configuredfor displaying a list of users participating in the session on theright-hand side of the display.

The next step, as represented by block 130, is logging event datarelated to a plurality of events associated with the problem definitioninitiative session. In some embodiments, for example, the event dataincludes data corresponding to one or more messages received from one ormore users and corresponding to a dialogue, such as a chat session. Asanother example, the event data may include data related to a log of themessages published via the interface and/or data related to the usersparticipating in and/or the users absent from the session. The nextstep, as represented by block 140, is initiating display of at leastsome of the event data via the interface.

Referring now to FIG. 1B, a flowchart illustrates a method 100Bincluding additional steps for information management related to aproblem definition initiative. In various embodiments, none, some or allthe steps discussed with reference to FIG. 1B are performed, and invarious embodiments, the steps performed are performed in the ordershown in FIG. 1B, and in some embodiments, are performed in differentorders. The first step, as represented by block 150, is archiving atleast a portion of the logged event data. The archived data, in variousembodiments, is configured for searching and is retrievable for reviewand further consideration by current/future users of the system. In someembodiments, some or all the data is archived locally to the informationmanagement system and in other embodiments, some or all the data isarchived remotely to the information management system. For example, insome embodiments, some or all the data is archived at a database remotefrom the information management system, and in some such embodiments,the information management system has access to the database for futuresearch and/or retrieval requests.

The next step shown, represented by block 155, is initiatingcommunication of an alert comprising information corresponding to anevent related to logged event data. For example, in various embodiments,initiating communication includes initiating a pager alert, initiating atext message alert, initiating an email alert, initiating social mediastatus update or other message, or the like.

The next step shown, represented by block 160, is initiating preparationof a report based at least in part on at least a portion of the loggedevent data or at least one of the received messages.

The next step shown, represented by block 165, is initiating a secondinterface in response to a request from a user, the second interfaceconfigured for receiving a plurality of messages from one or more of theplurality of users.

The next step shown, represented by block 170, is retrieving archiveddata from a datastore or database in response to a request from a userparticipating in the session. The archived data corresponds, in someembodiments, to a previously conducted session. In other embodiments,the archived data corresponds to an ongoing, current session. Thearchived data, in various embodiments, includes data such as sessiondata and/or event data previously logged or otherwise stored.

The next step shown, represented by block 175, is logging session datarelated to the session and initiating display of at least some of thesession data via the interface. In various embodiments, the sessiondata, for example, includes data corresponding to an identification of aproblem being addressed by the session. In various other embodiments,the session data, for example, includes data regarding the status of theproblem being addressed by the session. Such data may, in someembodiments, include one or more of data regarding whether the scope ofthe problem, that is, which lines of business it touches, the breadth ofthe problem, that is, how far into the infrastructure of each particularline of business the problem reaches, and/or whether the problem isprior, current and/or a future problem, among others.

The next step shown, represented by block 180, is initiating preparationof a report based at least in part on at least a portion of the datacorresponding to an identification of a problem being addressed by thesession. In various embodiments, the report may include informationregarding a status of the problem being addressed by the session asdiscussed above. Further, in various embodiments, the report may includeinformation regarding a status of one or more solutions or solutionsteps proposed to address the problem. The report prepared in step 160and/or in step 180, in various embodiments, can take any form, can be inany number of media and can be sent to one or more users.

Referring now to FIG. 2A, a flowchart illustrates a method 200A forinformation management related to a change deployment. For example, achange deployment may include introducing a new software product to allworkstations within a particular line of business of an enterprise. Inanother example, a change deployment may include providing users withinan organization a new methodology for dealing with a common everydayproblem such as a procedure for dealing with a printer having a jammedsheet. The first step of method 200A, as represented by block 210, isreceiving information comprising a plurality of messages from aplurality of users communicating via a plurality of workstations duringa change deployment session. The plurality of messages, in someinstances, is referred to as a dialogue, a chat or chatting session,similar to the problem initiative method discussed above. In variousother embodiments, however, the users may be communicating before and/orafter a change deployment has occurred. In fact, in some embodiments,for example, the information management system maintains the dialogueand, in some embodiments, other functionality of the system, before,during and after a change deployment.

The next step, as represented by block 220, is initiating an interfaceto one or more of the plurality of users including, for example,initiating display of at least one of the plurality of messages via theinterface. In another example embodiment, initiating the displayincludes initiating display of task data corresponding to at least onetask necessary for completing the change deployment. In variousembodiments, the interface includes one or more panels configured forproviding the user an easy view into desired information regarding thechange deployment. For example, in one embodiment, the interfaceincludes a first panel configured for displaying at least some of theevent data on the left-hand side of the display. Further, a second panelis configured for displaying at least one of the plurality of messagesin the middle of the display. Finally, a third panel is configured fordisplaying a list of users participating in the session on theright-hand side of the display. In various embodiments, differentconfigurations are initiated in order to provide the user with variouspieces of desired information regarding the change deployment. Forexample, in some embodiments only a first panel and a second panel aredisplayed, the first panel being configured for displaying informationregarding the change deployment in general, and the second panel beingconfigured for providing information such as the dialogue.

The next step, as represented by block 230, is logging event datarelated to a plurality of events associated with the change deploymentsession. The event data, in various embodiments, includes task statusdata indicating the status of the at least one task necessary forcompleting the change deployment. In various embodiments, the eventdata, for example, corresponds to one or more messages received from oneor more users.

The next step, as represented by block 240, is initiating display of atleast some of the event data via the interface.

Referring now to FIG. 2B, a flowchart illustrates a method includingadditional steps for information management related to a changedeployment. It should be noted that none, some or all the stepsdiscussed with reference to FIG. 2B may be included in variousembodiments of the invention, and in various embodiments, the stepsperformed are performed in the order shown in FIG. 2B, and in someembodiments, are performed in different orders. The first step shown,represented by block 250, is archiving at least a portion of the loggedevent data. The archived data, as discussed above, is archived in someembodiments remote to the system and in other embodiments proximal thesystem. In some embodiments, the archived data is archived such that itis searchable and retrievable by either current or future users of thesystem.

The next step shown, represented by block 255, is initiatingcommunication of an alert comprising information corresponding to anevent related to logged event data. That is, when an event occurs, suchas reaching a milestone or completing a task essential to the changedeployment, the system accepts input from a user regarding the event andlogs data corresponding to the event, which is called event data. Inother embodiments, one or more messages or other information is receivedby the system, and the system determines that an event has occurred. Forexample, in one embodiment, the system receives a message from a user inthe dialogue indicating that a goal has been achieved. The system isconfigured to monitor the dialogue in order to determine whether anysignificant events are discussed. Based on a textual analysis of themessages, the system can determine whether an event has occurred, and ifso, log data corresponding to the event. In some embodiments, the systemdetermines that an event probably occurred and confirms that the eventoccurred with one or more users of the system. For example, in oneembodiment, the system sends a user a private message requesting theuser confirm that a particular event has occurred.

The next step shown, represented by block 260, is initiating preparationof a report based at least in part on at least a portion of the loggedevent data or at least one of the received messages.

The next step shown, represented by block 265, is initiating a secondinterface in response to a request from a user. The second interface isconfigured, in some embodiments, for receiving a plurality of messagesfrom one or more of the plurality of users.

The next step shown, represented by block 270, is retrieving archiveddata from a database in response to a request from a user participatingin the session. The archived data, in some embodiments, corresponds to apreviously conducted session, and in other embodiments, corresponds toan ongoing, current session. The archived data, in various embodiments,includes data such as session data and/or event data previously loggedor otherwise stored.

The next step, represented by block 275, is logging session data relatedto the session and initiating display of at least some of the sessiondata via the interface. The session data, in various embodiments, forexample, may include data corresponding to an overall status of thechange deployment being addressed by the session. In various otherembodiments, the session data may include change deploymentidentification information such as a name of the change deployment or areference number for the change deployment or the like. In variousembodiments, the session data may include change deployment summaryinformation such as a brief prose description of the goals and/or tasksaddressed by the change deployment.

The next step shown, represented by block 280, is initiating preparationof a report based at least in part on at least a portion of the datacorresponding to task status data indicating the status of the at leastone task necessary for completing the change deployment. The reportprepared in step 260 and/or in step 280, in various embodiments, cantake any form, can be in any number of media and can be sent to one ormore users.

The next step shown, represented by block 285, is initiating display ofa plurality of required participants and the status, that is, whether ornot each of the plurality of participants are currently participating,have currently participated previously and/or have not participated.This display provides an element of accountability as well asinformation for those individuals participating in the session. First ofall, it provides a user the opportunity to anticipate the participantsnecessary for the change deployment and the session as well as providingusers the opportunity to view which individuals or lines of business areabsent from the session who are scheduled to be present. In this regard,the user may then follow up with the individuals and/or lines ofbusiness or otherwise make note of the absence of the individuals and/orlines of business.

Referring now to FIG. 3A, a flowchart illustrates a method 300A forinformation management related to deployment of a plurality of changes.In various embodiments, the system performing various steps of themethod 300A is referred to as a detailed task scheduler (DTS) system.The first step, as represented by block 310, is receiving informationcomprising initiative data corresponding to each of a plurality ofchanges. In some embodiments, the initiative data includes data relatingto a plurality of parameters corresponding to each of the plurality ofchanges. The information received relates to a multiple changedeployment session. In some embodiments, the information received alsoincludes a plurality of messages from a plurality of users communicatingvia a plurality of workstations during a multiple change deploymentsession. In some embodiments, similar to methods 100A and 200A discussedabove, the plurality of messages comprise a dialogue, also referred toas a chat or chatting session.

The next step, as represented by block 320, is initiating an interfaceto one or more of the plurality of users including, for example,initiating display of at least some of the initiative data. In someembodiments, as mentioned above, the initiative data may include one ofthe plurality of messages that are also displayed via the interface tothe users. For example, in some embodiments, the display includesmultiple panels configured for presenting various pieces of data to auser in a readily available format. In one embodiment, the first panelis configured for displaying at least some of the event data on theleft-hand side of the display, a second panel is configured fordisplaying at least one of the plurality of messages in the middle ofthe display, and a third panel is configured for displaying a list ofusers participating in the session on the right-hand side of thedisplay.

The next step, as represented by block 330, is logging event datarelated to a plurality of events associated with the multiple changedeployment session. The event data, in some embodiments, includes changestatus data indicating the status of the at least one of the pluralityof changes associated with the deployment. In some embodiments, eachchange is also related to task data that indicates the status of atleast one of the tasks required in order for the change to besuccessful. The event data, in some embodiments, also corresponds to oneor more messages received from one or more users. The next step, asrepresented by block 340, is initiating display of at least some of theevent data via the interface.

Referring now to FIG. 3B, a flowchart illustrates a method 300Bincluding additional possible steps for information management relatedto deployment of a plurality of changes. It should be noted that none,some or all the steps discussed with reference to FIG. 3B may beincluded in various embodiments of the invention, and in variousembodiments, the steps performed are performed in the order shown inFIG. 3B, and in some embodiments, are performed in different orders. Thefirst step shown, represented by block 350, is archiving at least aportion of the logged event data. The archived data, in variousembodiments, is configured for searching and retrieval in response to arequest from a user.

The next step shown, which is represented by block 355, is initiatingcommunication of an alert comprising information corresponding to anevent related to logged event data. For example, in some embodiments,initiating communication includes initiating a pager alert, initiating atext message alert, initiating an email alert, initiating social mediastatus update or message or the like.

The next step shown, represented by block 360, is initiating preparationof a report based at least in part on at least a portion of the loggedevent data or at least one of the received messages.

The next step shown, represented by block 365, is initiating a secondinterface in response to a request from a user, the second interfaceconfigured for receiving a plurality of messages from one or more of theplurality of users in various embodiments.

The next step shown, represented by block 370, is retrieving archiveddata from a database in response to a request from a user participatingin the session. In some embodiments, the archived data corresponds to apreviously conducted session, and in other emobodiments, the archiveddata corresponds to a current, ongoing session.

The next step shown, represented by block 375, is logging session datarelated to the session and initiating display of at least some of thesession data via the interface. In some embodiments, for example, thesession data includes data corresponding to an overall status of themultiple changes being deployed. For example, in one embodiment, theoverall status indicated a percentage toward the goal of completion ofall changes. In some embodiments, as another example, the session dataincludes multiple change deployment identification information. Forexample, in some such embodiments, the multiple change deploymentidentification information indicates the identity, such as a name orcodename, by which a particular change is referenced. In anotherexample, the multiple change deployment identification informationincludes information regarding the line of business or individualsassociated with each particular change, such as the individual orindividuals who initially identified the change as a valid response to aproblem, for example. In another example, the sessions may includemultiple change deployment summary information. The summary information,in various embodiments, may include information regarding each of thechanges being deployed during the release. The summary information mayinclude a short description of the change taking place, the tasksnecessary for the change to be completed, and the outlook for theaffected lines of business post change.

The next step shown, represented by block 380, is initiating preparationof a report based at least in part on at least a portion of the datacorresponding to an overall status of the multiple changes beingdeployed, the multiple change deployment identification information,and/or the multiple change deployment summary information. The reportprepared in step 360 and/or in step 380, in various embodiments, cantake any form, can be in any number of media and can be sent to one ormore users.

Referring not to FIG. 3C, a flowchart illustrates a method 300Cincluding additional possible steps for information management relatedto deployment of a plurality of changes. It should be noted that,similar to FIG. 3B, none, some or all the steps discussed with referenceto FIG. 3C may be included in various embodiments of the invention, andin various embodiments, the steps performed are performed in the ordershown in FIG. 3C, and in some embodiments, are performed in differentorders. The first step shown, represented by block 390, is initiatingdisplay of a plurality of required participants. Also, in variousembodiments, the status of each of the plurality of requiredparticipants is displayed. The interface, in some embodiments, asdiscussed above, includes multiple panels for separating and providinginformation in an easily-accessible format. In some embodimentsaccording to FIG. 3C, the interface includes a first panel and a secondpanel. The first panel is configured for displaying at least one of theplurality of messages and the second panel is configured for displayingthe plurality of required participants and the status, in someembodiments, of each of the plurality of required participants. Invarious embodiments, at least one of the plurality of requiredparticipants includes a line of business or one or more individuals.Also, in various embodiments, the status is selected from a previouslyactive status, a currently active status or a never active status.

The next step shown, represented by block 395, is receiving a pluralityof change initiative plans, each of the change initiative planscomprising the initiative data corresponding to a plurality of changes.

In one application, for example, numerous users associated withdifferent lines of business across an organization are scheduled to beinvolved in an enterprise-wide release or multiple change project. Eachof the users uploads parameters relating to one or more changesscheduled to occur during the release. The system receives thoseparameters and an interface is provided to the users that allows accessto information concerning some or all the scheduled changes before,during and/or after the scheduled release of the changes. The interface,in some embodiments, includes dialogue functionality and in someembodiments includes various panels and/or windows/pages for providinginformation concerning one or more of the changes.

Referring now to FIG. 4, an environment 400 in which an informationmanagement system 401 operates is illustrated. The informationmanagement system 400 may, in various embodiments be configured forperforming one or more of the methods 100, 200, and/or 300 including orexcluding one or more of the various steps disclosed above. In theconfiguration shown, the information management system 401 communicatesacross a network 420 with one or more remote devices, such asworkstation 440, workstation 430, laptop 450 and/or handheld device 460.This configuration is intended to illustrate that a user (not shown) caninteract with the information management system 401 using a variety ofremote devices. Furthermore, in some embodiments one or more users caninteract with the information management system 401 locally such asthrough an input/output device attached directly with the informationmanagement system 401.

The information management system 401, in various embodiments, has acommunication device 402 controlled by a processing device 404 in orderto communicate across the network 420. The network 420 is an intranet,the Internet, a local area network, a wide area network, and/or anyother electronic device network, and/or any combination of the same. Theprocessing device 404 is also in communication with a memory device 406configured for storing computer-readable instructions 408. Thecomputer-readable instructions, in various embodiments, include one ormore of a problem application 410, a change application 412, and/or adetailed task scheduler (DTS) application 414. In some embodiments, eachof these applications are contained within one application, and in otherembodiments, two of the application are contained within oneapplication. In various embodiments, one or more of the applications arestored remotely from the information management system 401 and accessedas necessary by the system 401 and/or any other device requiringinstructions. Further, in some embodiments, the memory device 406includes a datastore 416 configured for storing information and/or datasuch as the archived data discussed above. In other embodiments, thedatastore 416 is housed remotely and the information management system401 is in communication with the datastore 416.

Generally, in some embodiments, the method steps and/or sub-stepsdiscussed above with reference to FIG. 1A and FIG. 1B are embodied incomputer-executable instructions within the problem application 410. Insome embodiments, the method steps and/or sub-steps discussed above withreference to FIG. 2A and FIG. 2B are embodied in computer-executableinstructions within the change application 412. Finally, in someembodiments, the method steps and/or sub-steps discussed above withreference to FIG. 3A, FIG. 3B, and FIG. 3C are embodied incomputer-executable instructions within the DTS application.

Referring now to FIGS. 5A-5E, several screenshots of the informationmanagement system problem interface 500 are illustrated. The probleminterface 500 is also referred to herein and/or in the configurationshown as a problem portal, an incident portal and/or an incidentinterface. The configurations shown in FIGS. 5A-5E are oneimplementation embodiment of one or more of the method steps and/orsub-steps discussed with reference to FIGS. 1A and/or 1B, and/or othersteps and/or functions.

Referring now to FIG. 5A, a problem dashboard 501 of the probleminterface 500 is shown according to embodiments of the invention. In theembodiment shown, the problem dashboard 501 is configured for providinga listing of workrooms 506, each associated with a problem, incident orother matter being considered. The problem dashboard 501 includes anactive incidents tab 502 and a reconvened incidents tab 504. The activeincidents tab 502 directs the user to a listing of active incidents orproblems. In other words, the listing shown in FIG. 5A is a listing ofongoing, current problem workrooms 506. The problem dashboard 501includes a variety of information regarding each of the workrooms 506listed. For example, in the embodiment shown, the problem dashboard 501a workroom identification number 508, the geographic region 510 to whichthe problem pertains, the start date/time 512 of the problem workroom506, a brief description 514 of the problem and the host or leader 516of the problem workroom 506. The reconvened incidents tab 504 directsthe user to a listing of problem workrooms 506 that are notongoing/current. For example, a problem workroom 506 associated with aproblem that has been sufficiently defined may be included in thereconvened incidents listing. Additionally, various other types ofinformation may be included in the dashboard 501 in various embodiments.

Referring now to FIG. 5B, a create workroom page 518 of the probleminterface 500 is shown. The create workroom page 518 is configured forreceiving user input regarding creating a workroom corresponding to aproblem and, in some embodiments, to define parameters related to theproblem. In the configuration shown, the user can input a severityscore, a problem description, a related change number, the geographicregion of the organization's business to which the problem applies, anda domain for the problem. The related change number is a numberreferring to one or more changes associated or corresponding to theproblem. In other embodiments, additional or less information regardingthe problem may be inputted. The domain, as shown, refers to the type ofproblem, such as, for example, a problem regarding a banking center or aproblem regarding a bank card.

Referring now to FIG. 5C, a problem workroom 520 of the probleminterface 500 is shown. The problem workroom 520, as shown, is dividedinto three panels: a left-hand panel 522, a middle panel 524, and aright-hand panel 526. In various embodiments, the panels 522, 524,and/or 526 are configured to include the type(s) of information mostgermane to the issues encountered by the particular organization and/orone or more of its lines of business. In the embodiment shown, theleft-hand panel 522 is configured for displaying summary information 523regarding the incident such as identification information, severityinformation, workroom status information, start date/time information,problem/incident summary and/or description information and otherinformation. In various other embodiments, more or less information maybe displayed in the left-hand panel 522 depending on the specificconfiguration used and the specific problem workroom 520. The left-handpanel 522 also includes information concerning one or more bridgelinesassociated with the problem workroom 520, in some embodiments, so thatthose users desiring to enter a discussion regarding the problem can doso easily. In various embodiments, information regarding other types ofcommunication portal such as information regarding a chat room inaddition to the interface or multiple conference bridgelines is providedvia the interface. In some instances, the problem workroom 524 remainsactive concurrently with a bridgeline conference and, in fact, canremain active indefinitely. In some instances, multiple bridgelineconferences may be conducted using the same incident workroom. Such apattern may continue until the problem is sufficiently defined and/or asufficient change has been implemented or until one or more individualsdetermines the problem workroom 520 may be closed and/or moved into thereconvened problem listing.

In some embodiments, in addition to the summary information 523, theleft-hand panel also includes a detail window 529 including one or morefields for receiving user input.

For example, in one embodiment, the detail window 529 is configured forreceiving user input regarding some or all the summary information, suchthat, once a user has input information into the detail window 529, thatinformation is displayed as summary information 523. The detail window529 includes various fields for receiving user input, such as fieldsconfigured for receiving user input regarding choosing a restoral actionas well as fields for inputting customer impact, agent impact, workaround, restoral summary, next steps/follow up, root cause, and choosingthe geographic regions in which the problems have been restored. Arestoral action and/or restoral summary refer to actions, tasks,changes, and/or the like that are or were implemented in related to aproblem in order to remedy the problem or otherwise address the problem.In some embodiments, fields are provided for receiving user inputregarding which impacted sites have been restored, which impactedapplications are restored, which impacted domains are restored, and/orwhich impacted lines of business are restored. Impacted sites are thephysical business locations that were or are impacted by the problem. Insome embodiments, the summary information 523 and/or the detail window529 also includes information related to managers associated with theproblem workroom 506, such as a triage manager, an incident manager andthe like.

In addition to receiving and displaying various types of summaryinformation 523, the left-hand panel 522, in the embodiment shown, alsoincludes an input field 528 for receiving user input regarding loggingan action or an event. In the embodiment shown, the detail window 529provides a field for receiving user input regarding logging an action orevent. In this embodiment, a user can input an event for the system tolog, and potentially archive. Once the system receives the eventinformation from the user, it is generally referred to as event data.Event data relates to, for example, in some embodiments, datacorresponding to one or more events such as data being input by a userto the interface, one or more users joining the interface and/or exitingthe interface, one or more happenings within the organization recognizedby one or more automated systems. For example, in some embodiments,organization systems track particular happenings with regard toworkstation health, such as the number of viruses detected on aparticular class of machines. In some embodiments, if the number ofviruses detected and/or cleaning from a particular class of machinesexceeds a predetermined threshold, then the system automatically logsthat information and the interface logs that information as event data.

The event data is logged by the system, and as discussed below, in someembodiments, some or all the event data is also displayed and/orarchived. Logging the event data refers to either temporarily storingthe data and providing access to the data locally, that is either on theuser's machine and/or on the machine(s) implementing and/or initiatingthe interface, such as the information management system, by way of theproblem interface 501 or semi-permanently or permanently storing thedata locally, and in some embodiments, associating the data with aspecific problem workroom 506. On the other hand, archiving the data, insome embodiments, generally refers to a relatively more permanentstorage of the data such that a future user could, using the informationmanagement system, search and retrieve desired archived data from adatastore remote to the information management system and/or the user'sworkstation. In various other embodiments, in addition to receivingevent data generated from a user, the system can determine whether anevent should be logged automatically, such as by analyzing a messageposted by a user. For example, in one embodiment, a user posts a messageindicating that a particular action item has been completed, and thesystem analyzes the message and either flags the message foradministrator review or automatically interprets the message, ifpossible, to determine event data, thereafter logging the event data.

In some embodiments, such as the embodiment shown in FIG. 5C, theproblem workroom 520 includes a middle panel 524 configured for listinga plurality of messages. Messages can either be generated automaticallyby the system or are received by the problem interface 501 from one ormore users. For example, when a user, NAME1, joined the workroom, thesystem generated and published a message indicating the user has joinedthe workroom. Such a message, in some configurations, would beautomatically classified as a user activity, for example. As anotherexample, the user NAME1 input a message “Test message 1” that was alsopublished in the middle panel 524. Such a message would automatically beclassified as user activity as well. Furthermore, in some embodiments,the middle panel provides a user the opportunity to filter and/or sortthe plurality of messages based on whether the messages correspond toaction/timeline information, status updates, user activity and the like.In some embodiments, the user can input information regarding one ormore of these fields. For example, in one embodiment, a user can input amessage regarding the timeline for achieving an action item with regardto the project. Such a message would automatically be classified as a“timeline” message. Hence, when a user sorted the plurality of messagesusing the timeline button, such a message would be retrieved. In thisregard, such information may constitute event information/data, and thesystem processes such data accordingly, that is, by either confirmingits nature as event data and/or automatically logging it as event data.

In the embodiment shown, a right-hand column 526 is configured forproviding an active user listing 530 as well as an inactive user listing532. Thus, the right-hand panel 524 provides users information regardingthose users currently active in the workroom 506 as well as informationregarding those users not currently active in the workroom 506 but whoseactivity is expected. Such information can be useful at least indetermining how to proceed with regard to conference scheduling,discussions and the like.

Referring now to FIG. 5D, a problem search page 540 of the probleminterface 500 is shown. On the left-hand side of the page, a user'sinput is received regarding the type of search to perform. In theembodiment shown, several types of searches may be specified including aticket number search, a domain search, a site search, a region search,an application search, or a keyword search. In various otherembodiments, more or fewer search options are included, such as optionsto search individuals associated with a problem, severity of theproblem, start date/time of the problem and the like. As discussedabove, the domains associated with each particular problem indicate thefield or area within the organization that the problem affects. Forexample, where the organization is a financial institution, the list ofdomains may include payments, deposits, bank card, ATM, and the like.The sites generally refer to a city or town, whereas region generallyrefers to a greater geographic area such as a state, country or even acontinental or super-continental area. Applications generally refer to aparticular application in official use by an organization and some orall its lines of business and/or individual associates. Shown in FIG. 5Dare the search results 542 from a search performed for the keyword“testing”. On the left-hand side of the search results, each result isidentified by a problem workroom identification number 544.

Referring now to FIG. 5E, a problem report page 550 of the probleminterface 500 configured to facilitate preparing a report according to auser's request is shown. In the example shown, the report has beenprepared by receiving user input requesting the “Banking Center” domainand specifying start dates. In various embodiments, reports may begenerated based on a variety of data related to the various problems506. For example, in some embodiments, reports can be generated based onseverity of problems and region. In another example, reports can begenerated based on problem workroom status, that is, whether or not anactive workroom is associated with the problem. Furthermore, in someembodiments, the generated reports may be communicated using a varietyof methods. For example, in various embodiments, generated reports arecommunicated to desired individuals and/or lines of business or groupsof individuals using email, text message, social media update/message,or the like. In the embodiment shown, the report has been sent via emailas evidenced by the notification in the lower right-hand corner of thescreenshot.

Referring now to FIGS. 6A-6E, several screenshots of the informationmanagement system change interface 600 are illustrated. The changeinterface 600 is also referred to herein and/or in the configurationshown as a workplan interface, a workplan portal, and/or a changeportal. The configurations shown in to FIGS. 6A-6E are oneimplementation embodiment of one or more of the method steps and/orsub-steps discussed with reference to FIGS. 2A and/or 2B, and/or othersteps and/or functions.

Referring now to FIG. 6A, a change dashboard 601 of the change interface600 is shown according to embodiments of the invention. The changedashboard 601, in this embodiment, includes a listing 602 of changes606, wherein each change 606 in the list includes a workroomidentification link 604, asset management link 608, edit workplan link610, description 612, time information 614, current step information616, and current step status information 618. Choosing the workroomidentification link 604 takes the user to the specific workroomassociated with the change. Choosing the asset management link 608 takesthe user to the asset plan drafted in conjunction with a change workplanin order to manage the assets necessary for implementing the particularchange. Choosing the edit workplan link 610 takes the user to theworkplan associated with a particular change. The description fieldprovides the owner and/or administrator of each change to provide abrief description of the change. The start time and the end timeprovides the owner and/or administrator the opportunity to indicate thestart time of the change and the end time of the change. For example, ifthe change includes installing a new version of an application acrossthe organization's workstations, the start time may indicate the starttime of the implementation of the installation of the new version of thesoftware. Likewise, the end time may indicate the desired end time ofthe installation of the new version of the application. In anotherexample, the start time and the end time indicate the start time and theend time of a workroom and/or a bridgeline conference regarding thechange. The current step information, in various embodiments, includesinformation regarding the current workplan step. That is, each changeworkplan includes one or more tasks and/or milestones associated withachieving completion of the change. For example, in a change initiativeassociated with installed a new version of an application, installationof the new version of the application throughout all the workstationswithin a particular geographic area may constitute a task and/or amilestone. Current step information may also indicate more generally thestep of the change initiative, such as, for example, a gatheringinformation step, a planning step, a close to initiation of change step,an initiation of change step, a completion of change step, and/or apost-change step. In various other embodiments one or more of thepreceding may or may not be included in the various steps used in thecurrent step information of the change dashboard. This listing isprovided merely as an example implementation.

Referring now to FIG. 6B, a change workroom 620 of the change interface600 is shown. The change workroom 620, similar to the problem workroom520 discussed above, includes multiple panels, each for displayinginformation to users. A left-hand panel 622 is configured to displayinformation associated with the change 606. Various fields providesummary information such as the change identification number, theprimary contact name or nickname, the start time and end time of thechange implementation, a description of the change, the current statusof the change, and/or a listing 623 of tasks 625 associated withcompletion of the change. In various other embodiments, some or all thesummary information shown in FIG. 6B is included and/or otherinformation regarding a particular change may be included as well. Inthis embodiment, the left-hand panel 622 also includes a fieldconfigured for receiving user input in the form of notes as well as asend page button 624 configured to send a copy of the change workroom ora portion of the change workroom to a recipient via email, text message,social media update/message or the like.

The listing 623 of tasks 625 includes a drop-down input field configuredfor receiving user input regarding the status of a particular task, suchas, for example, whether the task is in progress, cancelled, started,completed or the like. The listing 623 also includes a field fordisplaying a description of the task, as well as the start date/time andthe end date/time of each individual task 625 associated with the change606 associated with the workroom 620.

The middle panel 624 is configured for displaying a plurality ofmessages received from the users as well as other notifications such aschanges to the task listing 623, notifications regarding active versusinactive users, and the like. As shown in the screenshot of FIG. 6B, theplurality of messages includes messages indicating updates regarding thestatus of various tasks included in the task listing 623. As with themiddle panel 524 of the problem workroom 520, the middle panel 624 ofthe change workroom 620 is configured for allowing the user to filterand/or sort the plurality of messages based on whether the messages werestatus updates, user activity or the like. Of course, the user can alsospecify to view all the messages.

The right-hand panel 626, similar to the right-hand panel 526 of theproblem workroom 520, includes an active user listing 628 and aninactive user listing 630.

Referring now to FIG. 6C, a workplan creator page 640 of the changeinterface 600 is shown. The workplan creator page 640 includes variousfields configured for receiving information from a change creator, orowner or administrator, with regard to the new change 606. For example,in the embodiment shown, the workplan creator page 640 includes fieldsfor receiving user input regarding a change identification number, adescription of the new change, a primary contact, an escalation contact,expected start and end times, actual start and end times, and/orpredicted impacts. In various other embodiments some or all these fieldsmay be provided or removed as well as the addition of other fieldsrequesting additional information regarding the change being created.Additionally, formatted schedules or other externally prepared documentsand/or files may be uploaded and associated with the change 606. Similarto the workplan creator page 640, the change interface 600 is configuredfor providing a workplan overview page configured for displaying theinformation previously input by a workplan creator.

Referring to FIG. 6D, a workplan editor page 650 configured tofacilitate a user editing particular information relating to the changeis shown. The workplan editor page 650 includes a variety of fieldsconfigured for receiving user input regarding a workplan associated witha change. From the workplan editor page 650, a user may navigate to theworkplan itself or may modify the listing of tasks, such as by changingthe order in which the tasks are listed. The user may also select linesof business (LOBs) for which each particular task applies, among otherpieces of information related to the tasks.

Referring now to FIGS. 7A-7F, several screenshots of the informationmanagement system DTS interface 700 are illustrated. The DTS interface700 is also referred to herein and/or in the configuration shown as aDTS portal, a release interface, and/or a release portal. Theconfigurations shown in FIGS. 7A-7F are one implementation embodiment ofone or more of the method steps and/or sub-steps discussed withreference to FIGS. 3A, 3B, and/or 3C, and/or other steps and/orfunctions.

Referring now to FIGS. 7A.1 and 7A.2 concurrently, a DTS summary page701 of the DTS interface 700 is shown according to embodiments of theinvention. The DTS summary page includes numerous pieces of informationassociated with multiple changes 606. The DTS interface 700 providesusers a high level picture of, in some embodiments, an organization-widerelease. An organization-wide release, in other words, is a short periodof time, such as a weekend, wherein an organization plans and schedulesmany different changes to take place. The DTS interface 700 provides acentralized repository and real-time tracking for information related tothe multiple changes, before, during and after the release.

Referring back to FIGS. 7A.1 and 7A.2 concurrently, the DTS summary page701 shown includes a change listing 702 including various pieces ofinformation regarding each of the changes 606 in the listing 702. First,a workplan link 704 is displayed and configured for navigating a user tothe workplan associated with a specific change 606. Other pieces ofinformation regarding each of the changes 606 are change identificationnumbers 706, descriptions 708, change status 710, communication comments711, total tasks 712A, total tasks outstanding 712B, total milestones714A, total milestones outstanding 714B, expected start data/time 716,actual start date/time 718, expected end data/time 720, and actual enddate/time 722. In various other embodiments, more or less informationregarding each of the changes 606 is displayed. As shown under the “DTSSummary” page header, a filtering mechanism 724 is configured forreceiving user input in order to filter the changes included in thelisting 702. For example, in the embodiment shown, the filteringmechanism 724 receives user input regarding start dates and times aswell as information regarding tasks in order to filter the changesincluded in the listing 702.

By choosing the communication comments 711 of a particular change 606,in some embodiments, the user is navigated to a page or a pop-upconfigured for receiving user input in the form of a comment. In someembodiments, the actual end data/time 722 field and/or the status 710field provides a link configured for navigating a user to an overduecontact detail page and/or pop-up configured for providing contactinformation to the user as well as, in some embodiments, providing theuser the opportunity to send a communication, such as an email, to oneor more of the contacts associated with an overdue task and/or change.Some information provided by the overdue contact page and/or pop-up mayinclude identification and/or contact information for a primary contact,secondary contact, escalation contact, and/or the like. The status 710field, in various embodiments includes entries such as “Failed”, “NotStarted”, “Cancelled” and the like. Some such entries, when the changesare overdue based on the expected end date/time 720 include links to theoverdue contact detail page and/or pop-up. Furthermore, in someembodiments, such as the embodiment shown, an export button 726 isconfigured for providing an export functionality to a user. For example,in one embodiment, choosing the export button 726 navigates the user toan export preferences page (not shown) providing the user an opportunityto choose export preferences, such as the format of the exported dataand/or report. In other embodiments, choosing the export button 726automatically creates an export report based on predetermined or lockedpreferences. For example, in the embodiment shown, choosing the exportbutton 726 automatically calls a spreadsheet program and populates aspreadsheet with data exported from the DTS summary page 701.

Referring now to FIG. 7B, another embodiment of a DTS summary page 730is shown. As illustrated, the layout of this embodiment of the DTSsummary page 730 is somewhat different from the layout the DTS summarypage 701 depicted in FIG. 7A. Notably, DTS summary page 730 includesquicklinks 732 to often used functions such as a communication link732A, configured to, for example, send a report to an individual viaemail, a searching link 732B, configured to, for example, search a DTSdatabase, and/or an overdue change indicator 732C, which in someembodiments, is configured to navigate a user to an overdue contact pageand/or pop-up. Additionally, in the embodiment shown, a domain field 734displays domain information associated with a particular change, adescription field 736 includes description links configured to directinga user to a description page and/or pop-up including a description ofthe change and/or task. Furthermore, the filter 738 includes additionalexample filtering fields and both an export filter button 740A as wellas a full export button 740B are provided. The export filter button 740Ais configured for directing the user to an export preferences page andthen exporting the information into an export page and/or an exportdocument based on the user's inputs into the filter 738 and the exportpreferences page. In another embodiment, the export filter button 740Ais configured for automatically producing an export page and/or exportdocument based on predetermined and/or automatic preferences. Similarly,the full export button 740B, is configured for directing the user to anexport preferences page and then producing an export page and/or exportdocument in some embodiments, and in other embodiments, the full exportbutton 740B, is configured for automatically generating an export pageand/or document based on the un-filtered information of in the listing702 of the DTS summary page 730.

Referring now to FIG. 7C, a plan loader page 750 of the DTS interface700 is shown. The plan loader page 750 includes a plan loading field 752configured for receiving a change workplan from a user. In someinstances, a release is scheduled well in advance of the actual release,and individuals in charge of various components or changes within arelease configure their plans well before the actual release takesplace. In this regard, some or all the change workplans are availablefor viewing from the DTS interface 700 before the release date. Further,as changes are made to the change workplans, new versions may beuploaded.

Referring now to FIG. 7D, an event summary page 756 of the DTS interface700 is shown. The event summary page 756 includes information related toa specific event, which is also referred to herein as a change. Forexample, in the configuration shown, task and milestone details areprovided, such as, number of task, status of tasks and percentage oftasks completed, among other information.

Referring now to FIG. 7E, an event management page 760 of the DTSinterface 700 is shown. The event management page 760 includes, in theembodiment shown, an event listing 762 including selected informationregarding each event or change in the listing 762, a domain informationlisting 764 configured for receiving user input regarding whether eachparticular domain is active with regard to a particular change.Furthermore, in the embodiment shown, a general information window 766as well as a notifications settings by contact window 768 are provided.The general information window 766 is configured to receive user inputregarding the event or change, and the notifications settings by contactwindow 768 is configured for receiving user input regarding notificationwith regard to the primary, secondary, escalation, and repeat escalationcontacts. Referring now to FIG. 7F, a task detail page 770 of the DTSinterface 700 is shown. The task detail page 770, in the embodimentshown, includes various detailed information with regard to a specifictasks associated with a change/event. In various embodiments of the DTSinterface 700, users can be assigned different permissions. For example,in one embodiment, an administrator can assign access permission to thevarious users such as general access, restricted access or no access. Inother embodiments, additional access permission parameters may bedefined, thereby limited an individual's access to particularinformation through the DTS interface 700.

According to embodiments of the invention, a method and system manageinformation relating to a change deployment in order to communicate someor all the information to a plurality of users. The method includesproviding an interface to users at workstations accessible by the users,receiving information comprising a plurality of messages from userscommunicating via the workstations during a change deployment session,initiating display of at least one of the messages to the users via theinterface, initiating display of task data to the users via theinterface, the task data corresponding to at least one task necessaryfor completing the change deployment, logging event data related to aplurality of events associated with the change deployment conferencesession, the event data comprising task status data indicating thestatus of the at least one task necessary for completing the changedeployment, and initiating display of at least some of the event data tothe users via the interface.

As used herein, a “processing device” generally refers to a device orcombination of devices having circuitry used for implementing thecommunication and/or logic functions of a particular system. Forexample, a processing device may include a digital signal processordevice, a microprocessor device, and various analog-to-digitalconverters, digital-to-analog converters, and other support circuitsand/or combinations of the foregoing. Control and signal processingfunctions of the system are allocated between these processing devicesaccording to their respective capabilities.

As used herein, a “communication device” generally includes a modem,server, transceiver, and/or other device for communicating with otherdevices directly or via a network, and/or a user interface forcommunicating with one or more users. As used herein, a “user interface”generally includes a display, mouse, keyboard, button, touchpad, touchscreen, microphone, speaker, LED, light, joystick, switch, buzzer, bell,and/or other user input/output device for communicating with one or moreusers.

As used herein, a “memory device” or “memory” generally refers to adevice or combination of devices including one or more forms ofnon-transitory computer-readable media for storing instructions,computer-executable code, and/or data thereon. Computer-readable mediais defined in greater detail herein below. It will be appreciated that,as with the processing device, each communication interface and memorydevice may be made up of a single device or many separate devices thatconceptually may be thought of as a single device.

As will be appreciated by one of skill in the art, the present inventionmay be embodied as a method (including, for example, acomputer-implemented process, a business process, and/or any otherprocess), apparatus (including, for example, a system, machine, device,computer program product, and/or the like), or a combination of theforegoing. Accordingly, embodiments of the present invention may takethe form of an entirely hardware embodiment, an entirely softwareembodiment (including firmware, resident software, micro-code, etc.), oran embodiment combining software and hardware aspects that may generallybe referred to herein as a “system.” Furthermore, embodiments of thepresent invention may take the form of a computer program product on acomputer-readable medium having computer-executable program codeembodied in the medium.

Any suitable transitory or non-transitory computer readable medium maybe utilized. The computer readable medium may be, for example but notlimited to, an electronic, magnetic, optical, electromagnetic, infrared,or semiconductor system, apparatus, or device. More specific examples ofthe computer readable medium include, but are not limited to, thefollowing: an electrical connection having one or more wires; a tangiblestorage medium such as a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), a compact discread-only memory (CD-ROM), or other optical or magnetic storage device.

In the context of this document, a computer readable medium may be anymedium that can contain, store, communicate, or transport the programfor use by or in connection with the instruction execution system,apparatus, or device. The computer usable program code may betransmitted using any appropriate medium, including but not limited tothe Internet, wireline, optical fiber cable, radio frequency (RF)signals, or other mediums.

Computer-executable program code for carrying out operations ofembodiments of the present invention may be written in an objectoriented, scripted or unscripted programming language such as Java,Perl, Smalltalk, C++, or the like. However, the computer program codefor carrying out operations of embodiments of the present invention mayalso be written in conventional procedural programming languages, suchas the “C” programming language or similar programming languages.

Embodiments of the present invention are described above with referenceto flowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products. It will be understood thateach block of the flowchart illustrations and/or block diagrams, and/orcombinations of blocks in the flowchart illustrations and/or blockdiagrams, can be implemented by computer-executable program codeportions. These computer-executable program code portions may beprovided to a processor of a general purpose computer, special purposecomputer, or other programmable data processing apparatus to produce aparticular machine, such that the code portions, which execute via theprocessor of the computer or other programmable data processingapparatus, create mechanisms for implementing the functions/actsspecified in the flowchart and/or block diagram block or blocks.

These computer-executable program code portions may also be stored in acomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the code portions stored in the computer readablememory produce an article of manufacture including instructionmechanisms which implement the function/act specified in the flowchartand/or block diagram block(s).

The computer-executable program code may also be loaded onto a computeror other programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer-implemented process such that the codeportions which execute on the computer or other programmable apparatusprovide steps for implementing the functions/acts specified in theflowchart and/or block diagram block(s). Alternatively, computer programimplemented steps or acts may be combined with operator or humanimplemented steps or acts in order to carry out an embodiment of theinvention.

As the phrase is used herein, a processor/processing device may be“configured to” perform a certain function in a variety of ways,including, for example, by having one or more general-purpose circuitsperform the function by executing particular computer-executable programcode embodied in computer-readable medium, and/or by having one or moreapplication-specific circuits perform the function.

While certain exemplary embodiments have been described and shown in theaccompanying drawings, it is to be understood that such embodiments aremerely illustrative of, and not restrictive on, the broad invention, andthat this invention not be limited to the specific constructions andarrangements shown and described, since various other changes,combinations, omissions, modifications and substitutions, in addition tothose set forth in the above paragraphs, are possible. Those skilled inthe art will appreciate that various adaptations, combinations, andmodifications of the just described embodiments can be configuredwithout departing from the scope and spirit of the invention. Therefore,it is to be understood that, within the scope of the appended claims,the invention may be practiced other than as specifically describedherein.

What is claimed is:
 1. A computer program product comprising anon-transient computer-readable memory comprising computer-executableinstructions for managing information, by providing a centralizedrepository of real-time, current information, relating to a changedeployment in order to communicate some or all the information to aplurality of users, the instructions comprising: instructions forreceiving information from each of a plurality of workstations through anetwork, comprising a plurality of messages from users communicatingduring a real-time change deployment session; instructions forinitiating a real-time change application interface running on each ofthe plurality of workstations, whereby the real-time interface ispresented to one or more of the plurality of users, the real-timeinterface comprising: task data corresponding to a plurality of tasksnecessary for completing the change deployment, the task datacomprising, for each of the plurality of tasks, a task descriptionfield, a status field for indicating a current status of the task, astart date field for indicating a start date corresponding to the taskand an end date for indicating an end date corresponding to any taskhaving a completed or cancelled status; and a first portion of theplurality of users comprising one or more of the plurality of users whoare participating in the change deployment session; and wherein, each ofthe one or more plurality of users can be assigned different accesspermissions limiting at least a portion of the plurality of users'access to information through the interface; instructions fordetermining, based on a textual analysis of message content of theplurality of messages from the plurality of users, that at least one ofthe plurality of events has occurred, the determining that the at leastone of the plurality of events has occurred comprising determining,based on the textual analysis of the plurality of messages from theplurality of users, event data associated with the at least one of theplurality of events has occurred; instructions for automatically and inreal-time, logging event data related to a plurality of eventsassociated with the change deployment conference session, in response todetermining that at least one of the plurality of events has occurred,the event data comprising task status data indicating the status of theat least one task necessary for completing the change deployment, thelogging event data further comprising determining, based on the textualanalysis of the plurality of message from the plurality of users, toautomatically log the event data determined for the at least one of theplurality of events that has occurred; instructions for initiatingdisplay of at least some of the event data to the users via thereal-time change application interface; instructions for archiving atleast a portion of the logged event data, wherein the archived data isconfigured as searchable and retrievable data; instructions fordetermining that an event related to logged event data has occurred, andin response, automatically initiating, communication of one or morealerts comprising information corresponding to the event; whereininstructions for determining that the event has occurred comprise:monitoring of the plurality of messages after logging event data;performing textual analysis of the plurality of messages to determinewhether any events essential to change deployment are discussed; andseeking confirmation that the event has occurred from a user through aprivate message; instructions for initiating a second change applicationinterface, the second interface configured for receiving a plurality ofmessages from one or more of the plurality of users; and instructionsfor initiating preparation of a report based at least in part on atleast a portion of the data corresponding to task status data indicatingthe status of the at least one task necessary for completing the changedeployment.
 2. The computer program product of claim 1, wherein theevent data comprises data corresponding to one or more messages receivedfrom one or more users.
 3. The computer program product of claim 1,wherein the real-time interface comprises a first panel and a secondpanel, the first panel configured for displaying at least some of theevent data and the second panel configured for displaying at least oneof the plurality of messages.
 4. The computer program product of claim1, wherein the plurality of messages comprises a dialogue among theplurality of users and wherein the event data corresponds to thedialogue, wherein the instructions for logging the event data compriseinstructions for logging data related to the dialogue and wherein theinstructions for initiating display of at least some of the event datacomprise instructions for initiating display of at least a portion ofthe logged dialogue.
 5. The computer program product of claim 1, whereinfor archiving at least a portion of the logged event data furthercomprises archiving the logged event data at a database remote from aninformation management system.
 6. The computer program product of claim1, wherein the instructions for initiating communication comprise one ormore of instructions for initiating a pager alert, instructions forinitiating a text message alert, instructions for initiating an emailalert, instructions for initiating social media status update andinstructions for initiating a social media message.
 7. The computerprogram product of claim 1, wherein the interface comprises a firstpanel and a second panel, the first panel configured for displaying atleast one of the plurality of messages and the second panel configuredfor displaying a list of users participating in the conference session.8. The computer program product of claim 1, wherein the interfacecomprises a first panel, a second panel and a third panel, the firstpanel configured for displaying at least some of the event data, thesecond panel configured for displaying at least one of the plurality ofmessages, and the third panel configured for displaying a list of userparticipating in the conference session.
 9. The computer program productof claim 8, wherein the first panel is disposed on the left-hand side ofthe second panel and the third panel is disposed on the right-hand sideof the second panel.
 10. The computer program product of claim 1,wherein the instructions further comprise: instructions for retrievingarchived data from a database in response to a request from a userparticipating in the conference session, the archived data correspondingto a previously conducted conference session.
 11. The computer programproduct of claim 1, wherein the instructions further comprise:instructions for logging session data related to the conference sessionand initiating display of at least some of the session data via theinterface.
 12. The computer program product of claim 11, wherein thesession data comprises data corresponding to an overall status of thechange deployment being addressed by the conference session, changedeployment identification information, or change deployment summaryinformation.
 13. The computer program product of claim 12, wherein theinstructions further comprise: instructions for initiating preparationof a report based at least in part on at least a portion of the datacorresponding to an overall status of the change deployment beingaddressed by the conference session, change deployment identificationinformation, or change deployment summary information.
 14. The computerprogram product of claim 1, the instructions further comprise:instructions for initiating display of a plurality of requiredparticipants, by: determining plurality of participants necessary forthe change deployment session; displaying the status of each of theplurality of required participants, wherein the status further comprisesat least whether or not each of the plurality of participants arecurrently participating, have currently participated previously or havenot participated and lines of business.
 15. A method for managinginformation, by providing a centralized repository of real-time, currentinformation, relating to a change deployment in order to communicatesome or all the information to a plurality of users, the methodcomprising: receiving, at a processing device of an InformationManagement System (IMS) from each of a plurality of workstations througha network, information comprising a plurality of messages from aplurality of users communicating during a real-time change deploymentsession; initiating, by a processing device of the IMS, a real-timechange application interface running on each of the plurality ofworkstations, whereby the real-time interface is presented to one ormore of the plurality of users, the real-time interface comprising: taskdata corresponding to a plurality of tasks necessary for completing thechange deployment, the task data comprising, for each of the pluralityof tasks, a task description field, a status field for indicating acurrent status of the task, a start date field for indicating a startdate corresponding to the task and an end date for indicating an enddate corresponding to any task having a completed or cancelled status;and a first portion of the plurality of users comprising one or more ofthe plurality of users who are participating in the change deploymentsession; wherein, each of the one or more plurality of users can beassigned different access permissions limiting at least a portion of theplurality of users' access to information through the interface;determining, by a processing device of the IMS, based on a textualanalysis of message content of the plurality of messages from theplurality of users, that at least one of the plurality of events hasoccurred, the determining that the at least one of the plurality ofevents has occurred comprising determining, based on the textualanalysis of the plurality of messages from the plurality of users, eventdata associated with the at least one of the plurality of events hasoccurred; in response to determining that at least one of the pluralityof events has occurred, automatically and in real-time, by a processingdevice of the IMS, logging event data related to a plurality of eventsassociated with the change deployment conference session, the event datacomprising task status data indicating the status of the at least onetask necessary for completing the change deployment, the logging eventdata further comprising determining, based on the textual analysis ofthe plurality of message from the plurality of users, to automaticallylog the event data determined for the at least one of the plurality ofevents that has occurred; wherein the real-time change applicationinterface further comprises initiating display of at least some of theevent data to the users via the interface; archiving, by a processingdevice of the IMS, at least a portion of the logged event data, whereinthe archived data is configured as searchable and retrievable data; inresponse to determining that an event related to logged event data hasoccurred, automatically initiating, by the processing device of the IMS,communication of one or more alerts comprising information correspondingto the event; wherein determining that the event has occurred comprises:monitoring of the plurality of messages after logging event data;performing textual analysis of the plurality of messages to determinewhether any events essential to change deployment are discussed; andseeking confirmation that the event has occurred from a user through aprivate message; initiating, by a processing device of the IMS, a secondchange application interface, the second interface configured forreceiving a plurality of messages from one or more of the plurality ofusers; and initiating, by a processing device of the IMS, preparation ofa report based at least in part on at least a portion of the datacorresponding to task status data indicating the status of the at leastone task necessary for completing the change deployment.
 16. The methodof claim 15, wherein the event data comprises data corresponding to oneor more messages received from one or more users.
 17. The method ofclaim 15, wherein the real-time change application interface comprises afirst panel and a second panel, the first panel configured fordisplaying at least some of the event data and the second panelconfigured for displaying at least one of the plurality of messages. 18.The method of claim 15, wherein the plurality of messages comprises adialogue among the plurality of users and wherein the event datacorresponds to the dialogue, wherein logging the event data compriseslogging data related to the dialogue and wherein initiating display ofat least some of the event data comprises initiating display of at leasta portion of the logged dialogue.
 19. The method of claim 15 wherein,archiving at least a portion of the logged event data further comprisesarchiving the logged event data at a database remote from the IMS. 20.The method of claim 15, wherein the initiating communication comprisesone or more of initiating a pager alert, initiating a text messagealert, initiating an email alert, initiating social media status updateand initiating a social media message.
 21. The method of claim 15,wherein the interface comprises a first panel and a second panel, thefirst panel configured for displaying at least one of the plurality ofmessages and the second panel configured for displaying a list of usersparticipating in the conference session.
 22. The method of claim 15,wherein the interface comprises a first panel, a second panel and athird panel, the first panel configured for displaying at least some ofthe event data, the second panel configured for displaying at least oneof the plurality of messages, and the third panel configured fordisplaying a list of user participating in the conference session. 23.The method of claim 22, wherein the first panel is disposed on theleft-hand side of the second panel and the third panel is disposed onthe right-hand side of the second panel.
 24. The method of claim 15,further comprising: retrieving archived data from a database in responseto a request from a user participating in the conference session, thearchived data corresponding to a previously conducted conferencesession.
 25. The method of claim 15, further comprising logging sessiondata related to the conference session and initiating display of atleast some of the session data via the interface.
 26. The method ofclaim 25, wherein the session data comprises data corresponding to anoverall status of the change deployment being addressed by theconference session, change deployment identification information, orchange deployment summary information.
 27. The method of claim 26,further comprising: initiating preparation of a report based at least inpart on at least a portion of the data corresponding to an overallstatus of the change deployment being addressed by the conferencesession, change deployment identification information, or changedeployment summary information.
 28. The method of claim 15, furthercomprising: initiating display of a plurality of required participants,by: determining plurality of participants necessary for the changedeployment session; displaying the status of each of the plurality ofrequired participants, wherein the status further comprises at leastwhether or not each of the plurality of participants are currentlyparticipating, have currently participated previously or have notparticipated and lines of business.